Method and system for establishing a communications pipe between a personal security device and a remote computer system

ABSTRACT

The present invention provides a method and a system for establishing a communications path (the “pipe”  75 ) over a communications network ( 45 ) between a Personal Security Device (PSD  40 ) and a Remote Computer System ( 50 ) without requiring means for converting high-level messages such as API-level messages to PSD-formatted messages such as APDU-formatted messages (and inversely) to be installed on a local Client ( 10 ) in which a PSD ( 40 ) is connected.

1. FIELD OF INVENTION

[0001] The present invention relates to a method and system for establishing a communications path (the “pipe”) over a communications network between a Personal Security Device (PSD) and a Remote Computer System.

2. BACKGROUND OF INVENTION

[0002] The current art involving the use of Personal Security Devices (PSD), for example, smart cards, subscriber identity module (SIM) cards, biometric devices, or combinations thereof, requires specialized messaging software or firmware to be installed on a local Client in which the PSD is connected. These specialized routines are used to translate messages from high-level messaging formats into low-level messaging formats (i.e. into PSD-formatted messages). An example of such routines is what is generally known in the art as an Application Protocol Data Unit (APDU) interface. Installing and maintaining APDU interfaces for a large number of local Clients can be a substantial and costly challenge in a multi-user organization. In addition, Client resources such as disk space, memory and computing resources are unnecessarily tied up by the software, which could be better utilized for other purposes.

[0003] Another significant limitation of the current art is that security mechanisms are implemented on a local Client to gain access to secure functions contained within a connected PSD. In a typical secure transaction with a PSD, a request is generated in the local Client by way of high-level software such as API-level software, which is subsequently encrypted in the Client and translated into APDU messaging format using an APDU interface, and sent to the PSD to access the intended secure function.

[0004] The potential exposure of secure information weakens the basic functionality of current PSDs, which is to protect private keys and other proprietary information from being unnecessarily disclosed. The limitations of the current art are such that localized key generating mechanisms, APDU interface software and transactions involving this software are potentially vulnerable to compromise by unauthorized programs running on the local Client or by other illicit means intending to monitor the key generation process and thus gaining access to security codes, algorithms and other sensitive data contained within the PSD or elsewhere. These limitations are magnified in a multi-user environment where the ability to control unauthorized access to local Clients and vulnerable software contained therein is increased.

3. SUMMARY OF INVENTION

[0005] It is an object of the present invention to provide a method for establishing a communications path (the “pipe”) over a communications network between a Personal Security Device (PSD) and a Remote Computer System without requiring means for converting high-level messages such as API-level messages to PSD-formatted messages such as APDU-formatted messages (and inversely) to be installed on a local Client in which a PSD is connected.

[0006] This object is achieved with a method for establishing a communications pipe between at least one PSD and at least one Remote Computer System over a network using at least one Client as a host to said at least one PSD, said at least one Client and said at least one Remote Computer System being in functional communications using a packet-based communications protocol over said network, said method comprising the steps of:

[0007] a) generating or retrieving, in said at least one Remote Computer System, a request to access said at least one PSD, said request being in a high-level messaging format,

[0008] b) converting, in said at least one Remote Computer System, said request from said high-level messaging format to a PSD-formatted request message,

[0009] c) encapsulating, in said at least one Remote Computer System, said PSD-formatted request message with said packet-based communications protocol, thus producing an encapsulated PSD-formatted request message,

[0010] d) transmitting said encapsulated PSD-formatted request message, using said packet-based communications protocol, from said at least one Remote Computer System to said at least one Client via said network,

[0011] e) extracting, in said *at least one Client, said PSD-formatted request message from said encapsulated PSD-formatted request message,

[0012] f) transmitting said PSD-formatted request message from said at least one Client to said at least one PSD,

[0013] g) processing, in said at least one PSD, said PSD-formatted request message, thus producing an PSD-formatted response message,

[0014] h) transmitting said PSD-formatted response message from said at least one PSD to said at least one Client,

[0015] i) encapsulating, in said at least one Client, said PSD-formatted response message with said packet-based communications protocol, thus producing an encapsulated PSD-formatted response message,

[0016] j) transmitting said encapsulated ADPU-formatted response message, using said packet-based communications protocol, from said at least one Client to said at least one Remote Computer System via said network,

[0017] k) extracting, in said at least one Remote Computer System, said PSD-formatted response message from said encapsulated PSD-formatted response message, and

[0018] l) converting, in said at least one Remote Computer System, said PSD-formatted response message into a high-level response message, and

[0019] m) processing said high-level response message in said at least one Remote Computer System.

[0020] With this method, conversion of high-level messages such as API-level messages to PSD-formatted messages such as APDU-formatted messages, and inversely, is made in the Remote Computer System. The local Client acts as a transparent host which allows a connected PSD to communicate with one or more Remote Computer Systems over a network.

[0021] By moving means for converting high-level messages such as API-level messages to PSD-formatted messages such as APDU-formatted messages (and inversely) from numerous local Clients to one or a few secure Remote Computer Systems, the overall data processing system is much easier to maintain and significantly less susceptible to unauthorized access or compromise.

[0022] The communications pipe generation may be initiated automatically upon connection of a PSD to a local Client, by a Client side request for access to information contained on another networked Client or Remote Computer System, or by a Remote Computer System requesting access to a PSD.

[0023] In this invention, PSD-formatted messages are preferentially encapsulated into a common communications protocols, such as TCP/IP, WAP, etc. which are used to communicate between one or more Clients with one or more Remote Computer Systems.

[0024] A program installed on each local Client and each Remote Computer System separates the incoming low-level PSD-formatted messages from the incoming message packets and routes the PSD-formatted messages to a connected PSD via its hardware device interface. In a multi-tasking operating environment, the Client is free to perform other data processing functions while transactions between a PSD and a Remote Computer System using the pipe are executed in the background. In situations where a firewall may mask individual Client network addresses, remote computer based pipe software should be installed on the proxy server. Other solutions common to virtual private networking may also be employed.

[0025] For purposes of this invention a Client may be any intelligent device such as a personal computer, laptop, cellular telephone, Personal Data Assistant (PDA), etc. which provides the network communications interface between a PSD and a Remote Computer System. A Remote Computer System includes any intelligent device which provides the necessary communications interface between networked devices and a PSD.

[0026] In a first embodiment of the invention, a communications pipe is formed when a Remote Computer System generates the proper PSD-formatted messages which are encapsulated into an agreed upon communications protocol, transmitted (broadcast for general polling or specific IP address of Client) over a network, invoking a reply by one or more PSDs which is (are) subsequently received by the requesting Remote Computer System. The latter described pipe formation process is equivalent to a handshake between a PSD and a Remote Computer System.

[0027] This first embodiment of the invention is useful in determining the status, identification and other derived information related to responding PSDs. For example, an APDU formatted polling command may be transmitted from the Remote Computer System over a network to all PSDs capable of receiving the command requesting each PSD to return its unique identification number or some other non-proprietary information. Based on the replies received, it is possible to determine which PSDs are active, their relative location, length of time each PSD has been active, network traffic information, etc. This first embodiment of the method of the invention does not require the use of secure communications protocols.

[0028] In a second embodiment of the invention, referred to as secure pipe generation, security mechanisms are employed to protect against unauthorized disclosure of proprietary information. The secure pipe generation process is equivalent to the pipe generating process described above but includes the added steps of generating cryptographically secured PSD-formatted messages, which are then encapsulated into a secure communications protocol, examples of which include TCP/IP with secure socket layer (SSL) encryption, IPSEC, etc. to generate a secure pipe between a Remote Computer System and a PSD.

[0029] In this second embodiment of the invention, PSD-formatted messages are encrypted using the proper keys to unlock secure applications and data contained within the secure domain of a PSD. Response PSD-formatted messages containing sensitive or proprietary information are likewise encrypted by the PSD and decrypted by the Remote Computer System.

[0030] The cryptographically secured PSD-formatted messages are encapsulated into outgoing message packets using the agreed communications secure protocol, sent over a network and routed through the PSD hardware interface by the Client and into the PSD as before. This second embodiment of the invention is useful in initializing a PSD, personalizing a PSD, accessing secure information contained within a PSD, changing, upgrading or deleting proprietary algorithms or data contained in a PSD, authenticating an end user, etc.

[0031] It is another object of the invention to provide a system for implementing the above-mentioned method.

4. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] A more complete understanding of the present invention may be accomplished by referring to the following Detailed Description and Claims, when viewed in conjunction with the following drawings:

[0033]FIG. 1—is a generalized system block diagram for implementing present invention (first embodiment),

[0034]FIG. 2—is a detailed block diagram depicting initiating a communications pipe where non-proprietary information is being requested (first embodiment),

[0035]FIG. 3—is a detailed block diagram depicting establishing a communications pipe where non-proprietary information is being requested (first embodiment),

[0036]FIG. 4A—is a generalized system block diagram for implementing present invention which includes software-based security mechanisms (second embodiment),

[0037]FIG. 4B—is a generalized system block diagram for implementing present invention which includes HSM based security mechanisms (second embodiment),

[0038]FIG. 5—is a detailed block diagram depicting initiating a secure communications pipe (second embodiment), and

[0039]FIG. 6—is a detailed block diagram depicting establishing a secure communications pipe (second embodiment).

5. DETAILED DESCRIPTION OF THE INVENTION

[0040] This invention provides a method and system to establish a remote communications pipe over a network between a Remote Computer System and a Personal Security Device connected to a host local Client. In this invention, Personal Security Devices (PSD) are intelligent devices such as smart cards, biometric devices, Subscriber Identification Module (SIM) cards, or combinations thereof having a microprocessor, runtime operating environment, an input/output communication port, memory storage including nonvolatile memory and random access memory and embedded software applications.

[0041] Two embodiments of the invention are described; a first embodiment (FIGS. 1 to 3) in which security mechanisms are not employed and a second embodiment (FIGS. 4A to 6) where security mechanisms are employed.

[0042] Note also that the following description of the invention will be based on a PSD which receives and sends APDU-(Application Protocol Data Unit)-formatted messages.

[0043] APDU messaging format, which is per se known in the art, is a lower-level messaging format which allows a PSD to communicate with higher-level applications located in devices to which the PSD is to be connected.

[0044] It must be clear that the present invention is not limited to the use of an APDU messaging format, and that any other low-level messaging format that can be processed by the PSD enters within the scope of the present invention.

[0045] In the appended claims, a message having such a format will be designated by the generic expression “PSD-formatted message”.

5.1. Detailed Description of a First Embodiment of the Invention

[0046] Referring now to FIG. 1, a generalized system block diagram of a first embodiment of the invention depicted. The various layers shown are based on the Open System Interconnection model (OSI). For simplicity, certain layers common to both the Client and Remote Computer System are not shown and should be assumed to be present and incorporated into adjacent layers. The layers common to both a Client and Remote Computer System include:

[0047] an Applications Layer 90 which generally contains higher level software applications (e.g. word processor) and a user interface and such as a Graphical User Interface (GUI),

[0048] an Applications Programming Interface (API) Layer 100 for processing and manipulating data for use by either higher or lower level applications,

[0049] a Communications Layer 105 which contains communications programs including secure communications capabilities, which enable a Client to communicate with a

[0050] Remote Computer System to exchange information in an agreed upon protocol and visa versa,

[0051] an Operating System Layer 110 or equivalent runtime environment, which controls the allocation and usage of hardware resources such as memory, Central Processing Unit (CPU) time, disk space, hardware I/O port assignments, peripheral device management,

[0052] a Hardware Drivers Layer 120 which permits the operating system to communicate and control physical devices connected to the Client's or Remote Computer System's hardware I/O bus,

[0053] and a Physical Device Layer 130 where Network Interface Cards (NIC) 140 provide the physical connections to a telecommunications network 45. Other Hardware Devices 80 may also be connected at this Layer.

5.1.1. Client Specific Features

[0054] A specialized program contained within the API Layer 100 of the Client and referred to as a Pipe Client 15, interacts with Communications Programs contained within the Communications Layer 105. The Pipe Client 15 functions to separate encapsulated APDU requests from incoming messaging packets received from a network 45 for processing by a locally connected PSD 40. Alternately, outbound APDU responses generated by a locally connected PSD 40, are processed by the Pipe Client for encapsulation into an agreed upon communications protocol by Communications Programs contained within the Communications Layer 105.

[0055] A software driver contained within the Communications Layer 105 of the Client and referred to as a PSD Software Interface 20 directs incoming APDUs communicated by the Pipe Client 15 into the I/O device port connecting the PSD Hardware Device Interface 25 to the locally connected PSD 40. Outgoing APDUs generated by the PSD are communicated through the PSD Hardware Device Interface 25 through the I/O device port to the PSD Software Interface 20 and subsequently communicated to the Pipe Client 15.

5.1.2. Remote Computer System Specific Features

[0056] A first specialized program contained within the API Layer 100 of the Remote Computer System 50 and referred to as an APDU Interface 55, translates higher level messaging formats into low-level APDU messaging format required to communicate with a PSD 40. Alternately, the APDU Interface 55 translates incoming APDU responses received from a PSD 40 into higher level messaging formats used by programs in the API Layer 100 and Applications Layer 90 of the Remote Computer System.

[0057] A second specialized program contained within the API Layer 100 of the Remote Computer System 50 and referred to as a Pipe Server 70 interacts with Communications Programs contained within the Communications Layer 105. The Pipe Server 70 functions to separate encapsulated APDU requests from incoming messaging packets received from a network 45 for processing by the APDU Interface 55. Alternately, outbound APDU requests translated by the APDU Interface 55 are processed by the Pipe Server for encapsulation into an agreed upon communications protocol by Communications Programs contained within the Communications Layer 105.

5.1.3. Other Inventive Features

[0058] The connection 30 between the PSD 40 and PSD Hardware Interface 25 includes but is not limited to traditional electrical or optical fiber connections or wireless means including optical, radio, acoustical, magnetic, or electromechanical. Likewise the connection 75 between the Client 10 and the network 45, and the connection 75 between the Remote Computer System 50 and the network 45 may be accomplished analogously.

[0059] The network, shown generally at 45, includes both public and private telecommunications networks connected by traditional electrical, optical, electro-acoustical (DTMF) or by other wireless means. Any mutually agreed upon communications protocol capable of encapsulating APDU commands may be employed to establish a communications pipe including open or secure communications protocols.

[0060] Referring now to FIG. 2, depicts initiating a communications pipe between the Remote Computer System 50 and the PSD 40 connected to a Client 10. In this depiction, the Remote Computer System 50 is sending a request to PSD 40 for non-proprietary embedded information 35, for example an identification number. PSD 40 is connected 30 to the local Client 10 using PSD Interface 25. PSD Interface 25 communicates with the Client 10 via hardware device port 5.

[0061] To initiate a communications pipe between Remote Computer System 50 and PSD 40, the Remote Computer System 50 generates a request 200 by way of API programs 100 which is translated into APDU format 220 by the APDU Interface 55 and sent to the Pipe Server 70 for message encapsulation. The encapsulated APDUs are then sent 210 to the Communications Programs 105S for incorporation into outgoing message packets 230.

[0062] The message packets 230 containing the encapsulated APDUs are transmitted 75 over the network 45 via a Network Interface Card (I/O) 130S. The Client 10 receives the message packets 240 containing the encapsulated APDUs which are received from the network 45 via a Network Interface Card (I/O) 130C installed on the local Client. The incoming messages are processed by Client-side Communications Programs 105C and routed 250 into the Pipe Client 15 for APDU extraction. The extracted APDUs are sent 260 through hardware device port 5, routed 270 into the PSD Interface 25 and sent to PSD 40 via connection 30 for processing within PSD domain 35.

[0063] Alternative requests to form a communications pipe 75 between a Remote Computer System 50 and a PSD 40 may be initiated by Client 10 requesting access to information contained on one or more networked local Clients, by connecting a PSD 40 to PSD Interface 25 which initiates a request to form a communications pipe 75, or by another Remote Computer System requesting access to PSD 40.

[0064] Referring now to FIG. 3, depicts a PSD response which establishes the communications pipe between PSD 40 and Remote Computer System 50. In this depiction, the request previously received is processed within the PSD domain 35, which generates a response message. The PSD response is sent in APDU format from PSD 40 through connection 30 and into PSD interface 25. The PSD response is then routed 370 through hardware device port 5 and sent 360 to the Pipe Client 15 for processing and encapsulation. The resulting message packets are then sent 350 to the Client-side Communications Programs 105C for incorporation into outgoing message packets 340. The message packets 340 containing the encapsulated APDUs are transmitted 75 over the network 45 via the Network Interface Card (I/O) 130C.

[0065] The Remote Computer System 50 receives the message packets 330 containing the encapsulated APDUs, which are received from the network 45 via the Network Interface Card (I/O) 130S installed on the Remote Computer System. The incoming messages are processed by server-side Communications Programs 105S and routed 310 into the Pipe Server 70 for APDU extraction. The extracted APDUs are sent 320 to the APDU Interface 55 for processing and translation into a higher-level format and sent 300 to API Level programs 100 for processing and further transactions with the PSD 40 if desired.

5.2. Detailed Description of a Second Embodiment of the Invention

[0066] Referring now to FIG. 4A, a generalized system block diagram of one implementation of a secure communications pipe is shown. The general system block diagram includes an additional software-based Cryptography Module 470 installed on the Remote Computer System, which is not shown in FIG. 1.

[0067]FIG. 4B depicts an alternative to using software-based security mechanisms. In this alternative embodiment of the invention, a Hardware Security Module (HSM) 440 is employed to perform cryptographic functions. To access the HSM, a software driver referred to as an HSM S/W Interface 475, is included in the API Layer 100. The HSM software driver communicates with a physical device interface included in the Physical Device Layer 130. The physical device interface is installed on the I/O bus of the Remote Computer System, and is referred to as an HSM H/W Interface 485. The HSM module 440 is connected 430 to the HSM H/W Interface a manner analogous to the PSD connection to the PSD Interface previously described. The use of HSM technologies provides end-to-end security, which further reduces the possibility of unauthorized disclosure of cryptographic or sensitive information.

[0068] Both APDU messaging security mechanisms shown in FIGS. 4A & 4B are used to generate cryptographic keys necessary to unlock secure functions and data contained within the secure domain of a PSD, encrypt outgoing APDUs and decrypt incoming encrypted APDUs. The security mechanisms employed in generating a secure pipe may include synchronous, asynchronous or any combination of cryptography methods.

[0069] Secure communications protocols used to communicate over a network are accomplished by the Communications Programs contained within the Communications Layers 105. Cryptography used in generating secure communications may employ the security mechanisms described for APDU messaging, employ separate mechanisms or employ any combination thereof.

[0070] Referring now to FIG. 5, depicts the initiating of a secure pipe between the Remote Computer System and the PSD 40 connected to Client 10. In this depiction, Remote Computer System 50 is sending a secure request to PSD 40 for proprietary embedded information 35, for example an authentication password. PSD 40 is connected 30 to the local Client 10 using PSD Interface 25. PSD Interface 25 communicates with the Client 10 via hardware device port 5.

[0071] To initiate a secure communications pipe between Remote Computer System 50 and PSD 40, a request 500 is generated on Remote Computer System 50 to access PSD 40 by way of API programs 100 which are translated into APDU format by the APDU Interface 55. The APDUs are then sent 520 to a Security Module 525 for encryption using a pre-established cryptography method. The proper cryptographic parameters may be determined by using a look-up table or database, which cross-references the PSD's unique internal identification information with one or more codes necessary to implement the appointed cryptography method.

[0072] The encrypted APDUs are then routed 510 to the Pipe Server 70 for message encapsulation. The encapsulated APDUs are then sent 530 to the Communications Programs 105 for processing, encryption using a pre-established secure communications protocol and incorporation into outgoing message packets 535. The secure message packets 535 containing the encrypted and encapsulated APDUs are transmitted 75 over the network 45 via a Network Interface Card (I/O) 130S.

[0073] The Client 10 receives the message packets 540 containing the encrypted and encapsulated APDUs which are received from the network 45 via a Network Interface Card (I/O) 130C installed on the local Client 10.

[0074] The incoming encrypted message packets are decrypted and processed using the pre-established cryptography employed in the secure communications protocol by Client-side Communications Programs 105C. The unencrypted message packets still containing the encrypted APDUs are routed 550 into the Pipe Client 15 for APDU extraction. The extracted APDUs are sent 560 through hardware device port 5, routed 570 into the PSD Interface 25 and sent to PSD 40 via connection 30 for decryption and processing within the secure domain 35 of the PSD 40. Using a pre-established cryptography method, incoming secure APDUs are decrypted and requests processed.

[0075] Referring now to FIG. 6, depicts a PSD secure response, which establishes the secure communications pipe between PSD 40 and Remote Computer System 50. In this depiction, the secure request previously received is processed within the secure domain 35 of the PSD 40, which causes the PSD to generate a secure response message using a pre-established cryptography method.

[0076] The PSD secure response is sent in APDU format from PSD 40 through connection 30 and into PSD interface 25. The PSD secure response is then routed 670 through hardware device port 5 and sent 660 to the Pipe Client 15 for processing and encapsulation. The resulting message packets are then sent 650 to the Client-side Communications Programs 105 for processing, encryption using a pre-established secure communications protocol and incorporation into outgoing message packets 640. The message packets 640 containing the encapsulated APDUs are transmitted 75 over the network 45 via the Network Interface Card (I/O) 130C.

[0077] The Remote Computer System 50 receives the message packets 635 containing the encapsulated APDUs from the network 45 via the Network Interface Card (I/O) 130S installed on the Remote Computer System 50. The incoming messages are processed and decrypted using the pre-established cryptography method employed in the secure communications protocol by the server-side Communications Programs 105 and routed 610 into the Pipe Server 70 for secure APDU extraction. The extracted secure APDUs are sent 630 to the Security Module 525 for decryption of the secure APDUs using the pre-established cryptography method. The decrypted APDUs are then routed 620 to the APDU Interface 55 for processing and translation into a higher-level format and sent 600 to API programs 100 for processing and further transactions with the PSD 40 if desired. This step establishes the secure “pipe” to communicate with the PSD. The secure pipe is maintained until the Remote Computer System signals the Client to close the hardware interface port 5.

[0078] No limitation is intended in the number of PSDs and Clients forming secure pipes 75 with one or more Remote Computer System(s) 50, nor should any limitation on the number of Remote Computer Systems 50 available for generating secure pipes 75 be construed from the drawings. Lastly, no limitation is intended concerning the initiating event to establish a communications pipe.

[0079] The foregoing described embodiments of the invention are provided as illustrations and descriptions. They are not intended to limit the invention to precise form described. In particular, it is contemplated that functional implementation of the invention described herein may be implemented equivalently in hardware, software, firmware, and/or other available functional components or building blocks. Other variations and embodiments are possible in light of above teachings, and it is not intended that the scope of the invention be limited by this Detailed Description, but rather by the Claims following herein. 

1. A method for establishing a communications pipe between at least one PSD (40) and at least one Remote Computer System (50) over a network (45) using at least one Client (10) as a host to said at least one PSD (40), said at least one Client (10) and said at least one Remote Computer System (50) being in functional communications using a packet-based communications protocol over said network (45), said method comprising the steps of: a) generating or retrieving, in said at least one Remote Computer System (50), a request (200; 500) to access said at least one PSD (40), said request (200; 500) being in a high-level messaging format, b) converting, in said at least one Remote Computer System (50), said request (200; 500) from said high-level messaging format to a PSD-formatted request message (220; 520), c) encapsulating, in said at least one Remote Computer System (50), said PSD-formatted request message (220; 520) with said packet-based communications protocol, thus producing an encapsulated PSD-formatted request message (210; 530), d) transmitting (230, 240; 535, 540) said encapsulated PSD-formatted request message (210; 530), using said packet-based communications protocol, from said at least one Remote Computer System (50) to said at least one Client (10) via said network (45), e) extracting, in said at least one Client (10), said PSD-formatted request message (260, 270; 560, 570) from said encapsulated PSD-formatted request message (250; 550), f) transmitting said PSD-formatted request message (260, 270; 560, 570) from said at least one Client (10) to said at least one PSD (40), g) processing, in said at least one PSD (40), said PSD-formatted request message (260, 270; 560, 570), thus producing a PSD-formatted response message (360, 370; 660, 670), h) transmitting said PSD-formatted response message (360, 370; 660, 670) from said at least one PSD (40) to said at least one Client (10), i) encapsulating, in said at least one Client (10), said PSD-formatted response message (360, 370; 660, 670) with said packet-based communications protocol, thus producing an encapsulated PSD-formatted response message (350; 650), j) transmitting (330, 340; 635; 640) said encapsulated PSD-formatted response message (350; 650), using said packet-based communications protocol, from said at least one Client (10) to said at least one Remote Computer System (50) via said network (45), k) extracting, in said at least one Remote Computer System (50), said PSD-formatted response message (320; 630) from said encapsulated PSD-formatted response message (310; 610), and l) converting, in said at least one Remote Computer System (10), said PSD-formatted response message (320; 630) into a high-level response message (300; 600), and m) processing said high-level response message in said at least one Remote Computer System (50).
 2. The method according to claim 1, further comprising the steps of: b1) encrypting said PSD-formatted request message (520) in said at least one Remote Computer System (50) after said step b) and before said step c), f1) decrypting said PSD-formatted request message (560, 570) in said at least one PSD (40) after said step f) and before said step g), g1) encrypting said PSD-formatted response message (660, 670) in said at least one PSD (40) after said step g) and before said step h), and k1) decrypting said extracted PSD-formatted response message (630) in said at least one Remote Computer System (50) after said step k) and before said step l).
 3. The method according to claim 2, wherein said at least one PSD (40) comprises unique identification information, comprising the step of cross-referencing said unique identification information with a look-up table in order to select proper cryptographic means for implementing said steps b1, f1, g1 and k1.
 4. The method according to claim 1, 2 or 3, comprising the step of initiating said communications pipe automatically upon connection of said at least one PSD (40) to said at least one Client (10).
 5. The method according to claim 1, 2 or 3, comprising the step of initiating said communications pipe upon an initial request generated by said at least one Client (10).
 6. The method according to claim 1, 2 or 3, comprising the step of initiating said communications pipe upon an initial request generated by at least one networked Remote Computer System.
 7. The method according to claim 1, 2 or 3, comprising the step of establishing said communications pipe in the background.
 8. The method according to claim 1, wherein said high-level messaging format is an API-level format, and wherein said PSD-formatted messages are APDU-formatted messages.
 9. A Client (10) for establishing a communications pipe between at least one PSD (40) and at least one Remote Computer System (50) over a network (45) using said Client (10) as a host to said at least one PSD (40), said Client (10) comprising: a) PSD interface means (25) for functionally connecting said at least one PSD (40) to said Client (10), b) Client communications means (105C) for transmitting and receiving messages over said network (45) using a packet-based-communications protocol, c) Client processing means (15) comprising: c1) means for receiving incoming message packets (250; 550) over said network (45) using said Client communications means (105C), for extracting incoming PSD-formatted messages (260, 270; 560, 570) from said incoming message packets (250; 550), and for transmitting said incoming PSD-formatted messages (260, 270; 560, 570) to said PSD (40) through said PSD interface means (25), and c2) means for receiving outgoing PSD-formatted messages (360, 370; 660, 670) coming from said PSD (40) through said PSD interface (25), for encapsulating said outgoing PSD-formatted messages (360, 370; 660, 670) into outgoing message packets (350; 650), and for transmitting said outgoing message packets (350; 650) over said network (45) using said Client communications means (105C).
 10. A Remote Computer System (50) for establishing a communications pipe between at least one PSD (40) and said Remote Computer System (50) over a network (45) using a Client (10) as a host to said at least one PSD (40), said Remote Computer System (50) comprising: a) Remote Computer System communications means (105S) for transmitting and receiving messages over said network using a packet-based-communications protocol, b) first Remote Computer System data processing means (55) for converting PSD-formatted messages into high-level messages, and inversely, c) second Remote Computer System data processing means (100) for implementing high-level programs, d) third Remote Computer System data processing means (70) comprising: d1) means for receiving incoming message packets (310; 610) over said network (45) using said Remote Computer System communications means (105S), for extracting incoming PSD-formatted messages (320; 630) from said incoming message packets (310; 610), and for transmitting said incoming PSD-formatted messages (320; 630) to said second Remote Computer System data processing means (100) through said first Remote Computer System data processing means (55), and d2) means for receiving outgoing PSD-formatted messages (220; 520) coming from said second Remote Computer System data processing means (100) through said first Remote Computer System data processing means (55), for encapsulating said outgoing PSD-formatted messages (220; 520) into outgoing message packets (210; 530), and for transmitting said outgoing message packets (210; 530) over said network (45) using said Remote Computer System communications means (105S).
 11. The Remote Computer System (50) according to claim 10, wherein said incoming PSD-formatted messages (630) are to be decrypted and said outgoing PSD-formatted messages (520) are to be encrypted, further comprising cryptographic means (440; 525) for decrypting said incoming PSD-formatted messages (630), and for encrypting said outgoing PSD-formatted messages (520).
 12. The Remote Computer System (50) according to claim 11, wherein said cryptographic means comprise a Hardware Security Module (440).
 13. A system for the establishment of a communications pipe, comprising at least one Client (10) according to claim 9 and at least one Remote Computer System (50) according to claim 10 functionally connected to said at least one Client (10) through said network (45).
 14. The system according to claim 13, further comprising at least one PSD (40) comprising: a) means for functionally connecting said at least one PSD to said PSD interface means (25), b) PSD communications means for transmitting and receiving PSD-formatted messages (260, 270, 360, 370) through said PSD interface means (25), and c) PSD processing means for interpreting incoming PSD-formatted messages (260, 270), executing commands included in said incoming PSD-formatted messages (260, 270) and transmitting outgoing PSD-formatted messages (360, 370) through said PSD interface (25) using said PSD communications means.
 15. A system for the establishment of a secure communications pipe, comprising at least one Client (10) according to claim 9 and at least one Remote Computer System (50) according to claim 11 functionally connected to said at least one Client (10) through said network (45).
 16. The system according to claim 15, further comprising at least one PSD (40) comprising: a) means for functionally connecting said at least one PSD (40) to said PSD interface means (25), b) PSD communications means for transmitting and receiving encrypted PSD-formatted messages (560, 570, 660, 670) through said PSD interface means (25), c) PSD cryptographic means for decrypting encrypted incoming PSD-formatted messages (560, 570) and for encrypting outgoing PSD-formatted messages (660, 670), and d) PSD processing means for interpreting said decrypted incoming PSD-formatted messages, executing commands included in said decrypted incoming PSD-formatted messages, and generating outgoing PSD-formatted messages to be encrypted by said PSD cryptographic means and transmitted through said PSD interface (25) using said PSD communications means. 